Hey @jsoref,

Could you push an empty commit to this branch to trigger the CI? It seems I can no longer approve the CI run

@mkmkme I've bumped the tip commit. hopefully that works

Please do not merge pull requests that have failing tests.

• Add Python 3.14, 3.14t, and PyPy-3.11 to the testing #35 (comment)

Please do not merge pull requests that have failing tests.

• Add Python 3.14, 3.14t, and PyPy-3.11 to the testing #35 (comment)

This is a misconfiguration of the GitHub repo. I'll look into it.

It is not a misconfiguration -- HOWTO is a typo.

HOW-TO or HOW TO would pass the spell checker.

I broadly use https://pypi.org/project/codespell.

It is not a misconfiguration -- HOWTO is a typo.

HOW-TO or HOW TO would pass the spell checker.

I broadly use https://pypi.org/project/codespell.

It is a misconfiguration since normally a PR with CI failing would not be merged.
I'll handle this failure and will configure the rules properly. No action is needed from your side.

• Fix typo in README.md for Unicode HOW-TO link #36

For the record, I selected that title because that's the title used by the linked document. It is not an unreasonable default to favor the title of a document when presenting a link.

The document in question is:
https://docs.python.org/3/howto/unicode.html#the-string-type

3.14.0 Documentation » Python HOWTOs » Unicode HOWTO

I don't personally care about the spelling of the item, but there is often a tendency in spelling tools not to enforce a spelling against the wishes of someone else. If my name is Josh, it's inappropriate to call me Joseph even if you don't have Josh in your dictionary (and yes, people have a tendency to do this, and yes I get rather angry when they do so).

Fwiw, my dictionary doesn't like HOWTO either.

There are some groups who insist on doing weird things to names where they rewrite colour into color even if the referenced thing has an opinion. If that's the style of a group, then that's ok. But, I personally don't favor that.

I'm sorry that we missed that the CI had an opinion. Given that it managed to not catch the other things I fixed, I personally don't have a particularly high opinion of the existing CI tooling, but I'm not actively trying to supplant it.

I would do codespell --ignore-words-list=howto in that tool. Can you propose a similar fix with your spell checker?

With mine, you just add items into .github/actions/spelling/expect.txt, as seen in https://github.com/check-spelling-sandbox/libvalkey-py/blob/spell-check-with-spelling/.github/actions/spelling/expect.txt

• Spelling #30 broke the build. Please add a new pull request which makes the Continuous Integration tests ✅ again.